Skip to content

Fix memory leak on get_map functions. #324

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

JaatadiaMulesoft
Copy link

No description provided.

Copy link

google-cla bot commented Jul 29, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@PiotrSikora
Copy link
Member

Hi! Thanks for finding the memory leak and providing this fix... Do you have a reproducer and/or test that we could add to the CI to catch this class of issues in the future?

@JaatadiaMulesoft
Copy link
Author

I was testing compiling the filter and deploying it, after some request you can clearly see that the memory starts to grow. Now checking If I can add a unit test, I've found several libraries that could be used for this mockalloc and allocation_counter, etc. Any suggestion?

Signed-off-by: Javier Atadia <[email protected]>
@JaatadiaMulesoft
Copy link
Author

Test added

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants